Data cache block deallocate requests

ABSTRACT

A data processing system includes a processor core supported by upper and lower level caches. In response to executing a deallocate instruction in the processor core, a deallocation request is sent from the processor core to the lower level cache, the deallocation request specifying a target address associated with a target cache line. In response to receipt of the deallocation request at the lower level cache, a determination is made if the target address hits in the lower level cache. In response to determining that the target address hits in the lower level cache, the target cache line is retained in a data array of the lower level cache and a replacement order field in a directory of the lower level cache is updated such that the target cache line is more likely to be evicted from the lower level cache in response to a subsequent cache miss.

BACKGROUND OF THE INVENTION

1. Technical Field

The present invention relates in general to data processing and moreparticularly to handling the processing of requests to deallocate a datacache block in a cache memory of a data processing system.

2. Description of the Related Art

A conventional multiprocessor (MP) computer system, such as a servercomputer system, includes multiple processing units all coupled to asystem interconnect, which typically comprises one or more address, dataand control buses. Coupled to the system interconnect is a systemmemory, which represents the lowest level of volatile memory in themultiprocessor computer system and generally is accessible for read andwrite access by all processing units. In order to reduce access latencyto instructions and data residing in the system memory, each processingunit is typically further supported by a respective multi-level cachehierarchy, with each lower level generally having a successively longeraccess latency. Thus, a level one (L1) cache generally has a loweraccess latency than a level two (L2) cache, which in turn has a loweraccess latency than a level three (L3) cache.

To provide a balance between competing design considerations such aspower dissipation, size, access latency and hit rates, many MP systemsimplement set-associative caches, which group cache entries incongruence classes each containing multiple entries for storing cachelines sharing a common address index. The removal (eviction) of cachelines from the entries in each congruence class is governed by areplacement policy, which is preferably selected to remove from thecongruence class the cache line least likely to again be accessed.Common replacement policies include least-recently used (LRU) andround-robin.

For some workloads, the replacement policy implemented by the cachehardware is supplemented by additional software management of thecache(s). For example, in some cases, a programmer or compiler caninsert explicit instructions in an application program to cause thecache hierarchy to invalidate particular cache lines or to flushparticular cache lines to system memory. Examples of cache managementinstructions from the PowerPC instruction set architecture are listed inTable I below.

TABLE I PowerPC Mnemonic Instruction name DCBF Flush Data Cache LineDCBI Invalidate Data Cache Line DCBZ Zero Data Cache Line ICBIInvalidate Instruction Cache Line

In some cases, explicit cache management instructions can causeinefficiency in execution of an application program, for example, byinvalidating a cache line or flushing the cache line to system memoryprior to the cache line being accessed again. In such cases, the accessto the cache line following the software-managed invalidation or flushwill incur significantly increased access latency as the cache line mustagain be retrieved from system memory, which may have an access latencythat is two orders of magnitude greater than the upper levels of thecache hierarchy.

SUMMARY OF THE INVENTION

In at least one embodiment, a data processing system includes aprocessor core supported by upper and lower level caches. In response toexecuting a deallocate instruction in the processor core, a deallocationrequest is sent from the processor core to the lower level cache, thedeallocation request specifying a target address associated with atarget cache line. In response to receipt of the deallocation request atthe lower level cache, a determination is made if the target addresshits in the lower level cache. In response to determining that thetarget address hits in the lower level cache, the target cache line isretained in a data array of the lower level cache and a replacementorder field in a directory of the lower level cache is updated such thatthe target cache line is more likely to be evicted from the lower levelcache in response to a subsequent cache miss in a congruence classincluding the target cache line.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is high level block diagram of an exemplary data processingsystem in accordance with one embodiment;

FIG. 2A is a high level block diagram of a processing unit from FIG. 1;

FIG. 2B is a more detailed block diagram of an exemplary embodiment of aprocessor core and associated cache hierarchy from FIG. 2A;

FIG. 3 illustrates an exemplary embodiment of a lower level cache memoryfrom FIG. 2B;

FIG. 4 depicts an exemplary embodiment of a cache directory of a lowerlevel cache;

FIG. 5 illustrates the operation of a compiler in accordance with oneembodiment;

FIG. 6 is a high level logical flowchart of an exemplary method ofcompiling source code to generate object code in accordance with oneembodiment;

FIG. 7 is a high level logical flowchart of an exemplary method by whicha processor core executes a deallocate instruction in accordance withone embodiment;

FIG. 8 is a high level logical flowchart of an exemplary method by whicha lower level cache processes a deallocation request in accordance withone embodiment;

FIG. 9 is a high level logical flowchart of an exemplary method by whicha lower level cache services a memory access request in accordance withone embodiment; and

FIG. 10 is a high level logical flowchart of an exemplary method bywhich a lower level cache services a cast-in request in accordance withone embodiment.

DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENT

With reference now to the figures and, in particular, with reference toFIG. 1, there is illustrated a high level block diagram of an exemplaryembodiment of a multiprocessor data processing system in accordance withthe present invention. As shown, data processing system 100 includesmultiple processing nodes 102 a, 102 b for processing data andinstructions. Processing nodes 102 a, 102 b are coupled to a systeminterconnect 110 for conveying address, data and control information.System interconnect 110 may be implemented, for example, as a busedinterconnect, a switched interconnect or a hybrid interconnect.

In the depicted embodiment, each processing node 102 is realized as amulti-chip module (MCM) containing four processing units 104 a-104 d,each preferably realized as a respective integrated circuit. Theprocessing units 104 a-104 d within each processing node 102 are coupledfor communication by a local interconnect 114, which, like systeminterconnect 110, may be implemented with one or more buses and/orswitches. Local interconnects 114 and system interconnect 110 togetherform an interconnect fabric, which preferably supports concurrentcommunication of operations of differing broadcast scopes. For example,the interconnect fabric preferably supports concurrent communication ofoperations limited in scope to a single processing node 102 andoperations broadcast to multiple processing nodes 102.

The devices coupled to each local interconnect 114 include not onlyprocessing units 104, but also one or more system memories 108 a-108 d.Data and instructions residing in system memories 108 can generally beaccessed and modified by a processor core (FIG. 2A) in any processingunit 104 in any processing node 102 of data processing system 100. Inalternative embodiments of the invention, one or more system memories108 can be coupled to system interconnect 110 rather than a localinterconnect 114.

Those skilled in the art will appreciate that data processing system 100can include many additional unillustrated components, such as peripheraldevices, interconnect bridges, non-volatile storage, ports forconnection to networks or attached devices, etc. Because such additionalcomponents are not necessary for an understanding of the presentinvention, they are not illustrated in FIG. 1 or discussed furtherherein. It should also be understood, however, that the enhancementsprovided by the present invention are applicable to data processingsystems of diverse architectures and are in no way limited to thegeneralized data processing system architecture illustrated in FIG. 1.

Referring now to FIG. 2A, there is depicted a more detailed blockdiagram of an exemplary processing unit 104 in accordance with thepresent invention. In the depicted embodiment, each processing unit 104includes multiple instances of a processor core and associated cachehierarchy, which are collectively identified by reference numeral 200.In the depicted embodiment, each processing unit 104 also includes anintegrated memory controller (IMC) 206 that controls read and writeaccess to one or more of the system memories 108 a-108 d within itsprocessing node 102 in response to requests received from processorcores and operations snooped on the local interconnect 114.

Still referring to FIG. 2A, each processing unit 104 also includes aninstance of coherence management logic 210, which implements a portionof the distributed snoop-based coherency signaling mechanism thatmaintains cache coherency within data processing system 100. Inaddition, each processing unit 104 includes an instance of interconnectlogic 212 for selectively forwarding communications between its localinterconnect 114 and system interconnect 110. Finally, each processingunit 104 includes an integrated I/O (input/output) controller 214supporting the attachment of one or more I/O devices, such as I/O device216. I/O controller 214 may issue operations on local interconnect 114and/or system interconnect 110 in response to requests by I/O device216.

With reference now to FIG. 2B is a more detailed block diagram of anexemplary embodiment of a processor core and associated cache hierarchy200 from FIG. 2A. Processor core 202 includes circuitry for processinginstructions and data. In the depicted embodiment, this circuitryincludes an instruction sequencing unit 201, which fetches instructionsfrom the memory hierarchy and orders the instructions for execution, andone or more execution units 203, which execute instructions receivedfrom ISU 203. In the depicted embodiment, execution units 203 include aload-store unit (LSU) 205 that executes memory access instructions andcache management instructions to calculate target addresses and togenerate corresponding memory access and cache management requestsspecifying the target addresses.

The operation of processor core 202 is supported by a cache memoryhierarchy implementing a weakly ordered storage architecture, meaningthat the cache memory hierarchy can generally perform store requestsreceived from the affiliated processor core 202 out-of-order withrespect to the program order of the associated store instructionsexecuted by the processor core 202 and only enforces ordering betweengroups of store requests separated by a barrier operation. The cachememory hierarchy includes a store-through level one (L1) cache 204within each processor core 202, a store-in level two (L2) cache 230(which is preferably inclusive of L1 cache 204), and a lookaside L3cache 232 that is utilized as a victim cache for L2 cache 230 andaccordingly is filled by cache lines evicted from L2 cache 230. Incontrast to many conventional victim cache arrangements, the contents ofL3 cache 232 are not exclusive of the contents of L2 cache 230, meaningthat a given memory block may be held concurrently in L2 cache 230 andL3 cache 232.

L3 cache 232 further includes at least one and preferably a plurality ofsnoop (SN) machine(s) 236 and at least one and preferably a plurality ofwrite inject (WI) machine(s) 238 within snooper 286 (see FIG. 2C). Asdiscussed further below, SN(s) 236 and WI(s) 238 handle the cast-in ofcache lines into L3 cache 232 in response to lateral castout (LCO)commands received from other L3 caches 232. In the described embodiment,SN(s) 236 are used to handle cast-ins that require no data movement andthus preferably do not include the inbound data management constructs,while WI(s) 238 are employed to handle LCO commands requiring datamovement and accordingly include inbound data management constructs(making them more costly than SN(s) 236). WIs 238 further handle theinjection of cache lines into L3 cache 232 by I/O devices 216.

FIG. 2B also illustrates an exemplary flow of requests, data andcoherence communication within the cache memory hierarchy of processorcore 202. In the depicted arrangement, dashed lines represent the flowof requests and coherence commands, and solid lines represent data flow.

As shown, processor core 202 transmits load requests 240 to, andreceives load data 242 from L2 cache 230. Processor core 202 alsotransmits store requests 244 and associated store data 246 to gatheringlogic 248, which gathers the store data associated with multiplerequests into one cache line of data and transmits the gathered storedata 249 to L2 cache 230 in conjunction with one gathered store request247. Although illustrated separately for clarity, gathering logic 248may be incorporated within processor core 202 and/or L2 cache 230.

In response to a memory access request from processor core 202, L2 cache230 assigns one of a plurality of read-claim (RC) machines 231 toservice the memory access request. Servicing the memory access requestmay entail the RC 231 of L2 cache 230 transmitting system coherencecommands 250 to coherence management logic 210 of FIG. 2A forcompilation and/or transmission on the interconnect fabric. The RC 231of L2 cache 230 may also transmit write data 254 to, and receives loaddata 252 from IMC 206 and/or interconnect logic 212. The RC 231 of L2cache 230 may also request load data from L3 cache 232 via a loadrequest 260 and receive load data 262 from L3 cache 232. L2 cache 230further includes a plurality of snoop (SN) machines 233 to servicememory access requests (e.g., read requests, read-with-intent-to-modifyrequests, and kill requests) snooped on the interconnect fabric.

To remove a cache line from L2 cache 230, L2 cache 230 may issue acast-in request to L3 cache 232, which in turn receives the cache lineas cast-in data 266. Similar to L2 cache 230, L3 cache 232 may interactwith IMCs 206 and/or cache memories in other cache hierarchies byissuing system coherence commands 270, receiving prefetch data 272and/or cast-in data 273, and/or transmitting write data 274.

Although the illustrated cache hierarchy includes only three levels ofcache, those skilled in the art will appreciate that alternativeembodiments may include additional levels (L4, L5, etc.) of on-chip oroff-chip in-line or lookaside cache, which may be fully inclusive,partially inclusive, or non-inclusive of the contents the upper levelsof cache. Further, any of the various levels of the cache hierarchy maybe private to a particular processor core 202 or shared by multipleprocessor cores 202. For example, in some implementations, the cachehierarchy includes an L2 cache 230 for each processor core 202, withmultiple of the L2 caches 230 sharing a common L3 victim cache 232.

With reference now to FIG. 3, there is illustrated a high level blockdiagram of an exemplary embodiment of one of L2 caches 230. (L3 caches232 may be similarly implemented.) As shown, L2 cache 230 includes adata array 302 and a directory 308 of the contents of data array 302,embodiments of which are described in greater detail below withreference to FIG. 4. L2 cache 230 also includes additional control logic(collectively referred to in the art as a “cache controller”), which inthe depicted embodiment includes multiple (e.g., 16) Read-Claim (RC)machines 231 a-231 n for independently and concurrently servicing load(LD) and store (ST) requests received from the affiliated processor core202. In order to service remote memory access requests originating fromprocessor cores 202 other than the affiliated processor core 202, thecontrol logic of L2 cache 230 includes multiple snoop (SN) machines 233a-233 m. Each snoop machine 233 can independently and concurrentlyhandle a remote memory access request “snooped” from local interconnect114. As will be appreciated, the servicing of memory access requests byRC machines 312 may require the replacement or invalidation of memoryblocks within data array 302. Accordingly, L2 cache 230 includes CO(castout) machines 310 that manage the removal and writeback of memoryblocks from data array 302.

The control logic of L2 cache 230 further includes an arbiter 305 thatcontrols multiplexers M1-M2 to order the processing of local memoryaccess and cache management requests received from affiliated processorcore 200 and remote requests snooped on local interconnect 114. Requestsare forwarded in accordance with the arbitration policy implemented byarbiter 305 to a dispatch pipeline 306 in which each request isprocessed with respect to directory 308 over a given number of cycles.

The control logic of L2 cache 230 also includes an RC queue (RCQ) 320and a Castout Push Intervention (CPI) queue 318 that respectively bufferdata being inserted into and removed from data array 302. RC queue 320includes a number of buffer entries that each individually correspond toa particular one of RC machines 231 such that each RC machine 231 thatis dispatched retrieves data from only the designated buffer entry.Similarly, CPI queue 318 includes a number of buffer entries that eachindividually correspond to a particular one of the castout machines 310and snoop machines 233, such that each CO machine 310 and each snoopmachine 233 that is dispatched retrieves data from only the respectivedesignated CPI buffer entry.

Each RC machine 231 also has assigned to it a respective one of multipleRC data (RCDAT) buffers 322 for buffering a memory block read from dataarray 302 and/or received from local interconnect 114 via reload bus323. The RCDAT buffer 322 assigned to each RC machine 312 is preferablyconstructed with connections and functionality corresponding to thememory access requests that may be serviced by the associated RC machine312. At least some of RCDAT buffers 322 have an associated store datamultiplexer M4 that selects data bytes from among its inputs forbuffering in the RCDAT buffer 322 in response unillustrated selectsignals generated by arbiter 305.

In operation, processor store requests comprising a transaction type(ttype), target real address and store data are received from theaffiliated processor core 202 within a store queue (STQ) 304. From STQ304, the store data are transmitted to store data multiplexer M4 viadata path 324, and the store type and target address are passed tomultiplexer M1. Multiplexer M1 also receives as inputs processor loadand deallocation requests sent by processor core 202 via load pipeline325 and directory write requests sent by RC machines 312. In response tounillustrated select signals generated by arbiter 305, multiplexer M1selects one of its input requests to forward to multiplexer M2, whichadditionally receives as an input a remote request received from localinterconnect 114 via remote request path 326. Arbiter 305 scheduleslocal and remote requests for processing and, based upon the scheduling,generates a sequence of select signals 328. In response to selectsignals 328 generated by arbiter 305, multiplexer M2 selects either thelocal request received from multiplexer M1 or the remote request snoopedfrom local interconnect 114 as the next request to be processed.

Still referring to FIG. 3, the request selected for processing byarbiter 305 is placed by multiplexer M2 into dispatch pipeline 306.Dispatch pipeline 306 preferably is implemented as a fixed durationpipeline in which each of multiple possible overlapping requests isprocessed for a predetermined number of clock cycles.

During the first cycle of processing within dispatch pipeline 306, a1-cycle directory read is performed utilizing the target address of therequest to determine if the target address hits or misses in directory308, and if the target address hits, the coherency state of the memoryblock within directory 308. The directory information, which includes ahit/miss indication and the coherency state of the memory block, isreturned by directory 308 to dispatch pipeline 306. As will beappreciated, no action is generally taken within an L2 cache 230 inresponse to miss on a remote memory access request; such remote memoryrequests are accordingly discarded from dispatch pipeline 306. However,in the event of a hit or miss on a local request or a hit on a remotememory access request, L2 cache 230 will service the request, which forrequests that cannot be serviced entirely within processing unit 104,may entail communication on local interconnect 114.

At a predetermined time during processing of a memory access requestwithin dispatch pipeline 306, arbiter 305 transmits the request addressto data array 302 via address and control path 330 to initiate a cacheread of the target cache line specified by the target address, thusdissipating additional power. The memory block read from data array 302is transmitted via data path 342 to Error Correcting Code (ECC) logic344, which checks the memory block for errors and, if possible, correctsany detected errors. For processor load requests, the memory block isalso transmitted to load data multiplexer M3 via data path 340 forforwarding to the affiliated processor core 202.

At the last cycle of the processing of a memory access request withindispatch pipeline 306, dispatch pipeline 306 makes a dispatchdetermination based, for example, on (1) the presence of an addresscollision between the target address and a previously received targetaddress currently being processed by a castout machine 310, snoopmachine 233 or RC machine 231, (2) the directory information, and (3)availability of an RC machine 231 or snoop machine 233 to process thememory access request. If dispatch pipeline 306 makes a dispatchdetermination that the memory access request is to be dispatched, thememory access request is dispatched from dispatch pipeline 306 to an RCmachine 231 or a snoop machine 233. If the memory access request failsdispatch, the failure is signaled to the requestor (e.g., local orremote processor core 202) by a retry response. The requestor maysubsequently retry the failed memory access request, if necessary.

While an RC machine 231 is processing a local memory access request, theRC machine 231 has a busy status and is not available to service anotherrequest. While an RC machine 231 has a busy status, the RC machine 231may perform a directory write to update the relevant entry of directory308, if necessary. In addition, the RC machine 231 may perform a cachewrite to update the relevant target cache line stored in data array 302.The directory write and data array write may be scheduled by arbiter 305during any interval in which dispatch pipeline 306 is not alreadyprocessing other requests according to the fixed scheduling of directoryreads and data array reads. When all operations for the given localmemory access request have been completed, the RC machine 312 returns toan unbusy state and is thus available for dispatch to service anotherrequest.

Referring now to FIG. 4, there is depicted a more detailed block diagramof an exemplary embodiment of data array 302 and directory 308 and of anL2 cache 230. (The data array of L3 caches 232 may be implementedsimilarly.) In the depicted embodiment, data array has a set-associativeorganization and accordingly including multiple ways 400 a-400 n. Eachway 400 includes multiple entries 402, which in the depicted embodimenteach provide temporary storage for up to a full memory block of data,e.g., 128 bytes. Each cache line or memory block of data is logicallyformed of multiple granules 404 (in this example, four granules of 32bytes each) that may correspond in size, for example, to the smallestallowable access to system memories 108 a-108 d. In some embodiments,granules 404 may be individually accessed and cached in data array 302.

As in conventional set-associative caches, memory locations in systemmemories 108 are mapped to particular congruence classes within dataarrays 302 utilizing predetermined index bits within the system memory(real) addresses. The particular cache lines stored within data array302 are recorded in cache directory 302, which contains one directoryentry 410 for each cache line in data array 302. As understood by thoseskilled in the art, each directory entry 410 in directory 308 comprisesat least a tag field 412, which specifies the particular cache linestored in the corresponding entry 402 of data array 302 utilizing a tagportion of the corresponding real address, a state field 414, whichindicates the coherence state of the cache line (e.g., according to thewell-known MESI coherency protocol or a variant thereof), and areplacement order field 416.

Replacement order field 416 includes a chronology field 418 indicating arelative replacement order for the cache line with respect to othercache lines in the same congruence class. In addition, in some (but notall) embodiments, replacement order field 420 further includes atransient (T) field 420, which if set, indicates that the associatedcache line has been the target of a deallocation request of theaffiliated processor core 202 and accordingly should be preferred fordeallocation from the cache hierarchy (e.g., as the Least Recently Usedmember or other preferred replacement order position).

With reference now to FIG. 5, there is illustrated an exemplary dataflow diagram of a process by which a compiler compiles source code withan explicit deallocate instruction that identifies a target cache lineto be preferentially deallocated from a cache memory hierarchy. In thedepicted process, program code, such as compiler 500, which is stored ona tangible computer-readable storage medium 502 such as disk or memorystorage, executes on a data processing system (e.g., data processingsystem 100 of FIG. 1) to receive pre-processed code such as source code502 or intermediate code, to compile the pre-processed code, and tooutput post-processed code such as object code 506.

As indicated, source code 504 includes an initialization instruction 510that initializes a loop variable x of a processing loop 512 to aninitial value (e.g., 0). In processing loop 512, source code 504includes a LOAD command 514 that specifies a dataset (e.g., a firstarray or database) to be loaded from a memory hierarchy and one or morecommands represented by PROCESS command 516 that specify processing tobe performed on the dataset. Processing loop 512 further includesinstruction 518, which increments the loop variable, and a BRANCHcommand 520 that causes processing loop 512 to iterate if the loopvariable has not attained a terminal value (represented by variable y).

Referring now to FIG. 6, there is depicted a high level logicalflowchart of an exemplary process by which program code, such ascompiler 500, processes pre-processed code, such as source code 504, toobtain post-processed code, such as object code 506. As with the otherlogical flowcharts presented herein, the illustrated operations aredepicted in a logical rather than chronological order. Consequently, inmany cases, certain of the operations shown may be performedconcurrently and/or in a different order than that illustrated. Theillustrated process can be performed, for example, as part of the codeoptimization operations of compiler 500.

As shown, the process begins at block 600 and then proceeds to blocks602-604, which depicts compiler 500 scanning a section of source code504 to detect termination of processing of a dataset. For example, inexemplary source code 504 the end of processing of a dataset may bedetected when the end of an iteration of processing loop 512 is reached.If compiler 500 fails to detect the end of a processing of a dataset inthe current section, the process passes to block 612, which illustratescompiler 500 determining whether its scan of source code 504 iscomplete. If so, the process illustrated in FIG. 6 terminates at block614. If, however, compiler 500 determines at block 612 that its scan ofsource code 504 is not complete, the process returns to block 602, whichhas been described.

Referring again to block 604, in response to compiler 500 detecting theend of processing a dataset, compiler 500 inserts into object code 506one deallocate instruction (referred to herein as a Data Cache BlockDeallocate (DCDB)) for each cache line in the dataset that has completedprocessing. Following block 610, the process passes to block 612, whichhas been described.

Referring again to FIG. 5, the exemplary portion of object code 506depicted in FIG. 5 includes a first load sequence 530 of multiple load(LD) instructions generated by compiler 500 to implement the initialiteration of LOAD command 514. As indicated, load sequence 530 loads then+1 elements of Dataset_(—)0 from system memories 108 into the registersand cache hierarchy of a processor core 202. Following load sequence530, compiler 532 has included in object code 506 one or moreinstructions 532 that implement the processing represented by PROCESScommand 516. Thereafter, as described with reference to block 610,compiler 500 inserts into object code 506 a deallocation sequence 534,which preferably includes a deallocate (e.g., DCBD) instruction for eachof the n+1 elements of Dataset_(—)0. Thereafter, compiler 500 inserts asecond load sequence 536 including multiple LD instructions to implementthe next iteration of LOAD command 514 by loading the n+1 elements ofDataset_(—)1 from system memories 108 into the registers and cachehierarchy of a processor core 202.

It should be noted that, in addition to being generated automatically bya compiler as shown in FIG. 5, deallocate instructions may alternativelyor additionally be directed coded by a human coder or an automated codegenerator. Further, it should be noted that if a deallocate instructionis erroneously inserted in object code 506 prior to the last referenceto the target cache line of the deallocate instruction (e.g., compiler500 inserts a DCBD instruction targeting data element[0,n] prior to aninstruction referencing data element[0,n] in the processing of dataelement[1,0]), the premature inclusion of a deallocate instruction doescause any processing error and does not necessarily diminish theperformance of the instruction subsequently referencing the data elementby increasing access latency. Access latency is not necessarilyincreased because the deallocate instruction does not force deallocationof the target cache line, but merely makes deallocation more likely.Thus, depending on address access patterns and hit rates, a target cacheline of a deallocate instruction may be retained in cache memory formany cache accesses following execution of the deallocate instruction,enabling a subsequent instruction to potentially access the target cacheline without incurring the latency penalty associated with againretrieving the target cache line from system memory.

With reference now to FIG. 7, there is illustrated a high level logicalflowchart of an exemplary method by which a processor core 202 executesa deallocate instruction in accordance with one embodiment. The processbegins at block 700 and then proceeds to block 702, which illustratesISU 201 of a processor core 202 retrieving a next instruction group forexecution from the memory hierarchy. ISU 201 decodes the instructions inthe instruction group and, as shown at block 704, determines if any ofthe instructions in the instruction group is a deallocate instruction(e.g., DCBD). For instructions other than deallocate instructions, ISU201 performs possibly conventional processing, as shown at block 706.ISU 201 dispatches the deallocate instruction(s) in the instructiongroup to LSU 205 (block 710), which executes each deallocate instructionto compute the target address of the target cache line of the deallocateinstruction (block 712). After possible translation of the targetaddress (e.g., effective-to-real translation) computed by LSU 205,processor core 202 sends a deallocation request corresponding to thedeallocate instruction to its affiliated L2 cache 230 (block 714),regardless of whether or not the target address hits in L1 cache 204. Asnoted above, the deallocation request, which preferably specifies a loadtransaction type and the computed target address, is preferablytransmitted to L2 cache 230 via load pipeline 325. One consequence ofimplementing the deallocation request as a load-type request rather thana store-type request is that the deallocation request affects thecaching of the target cache line in only the cache hierarchy of theparticular processor core 202 that executes the corresponding deallocateinstruction. Consequently, processing of the deallocation request is notdelayed by making the deallocation request visible to all cachehierarchies throughout data processing system 100 or the presence ofbarrier operations (e.g., SYNCs) utilized in the presence of aweakly-ordered storage system to synchronize storage-modifyingoperations across all cache hierarchies and system memories 108.Following block 714, the process depicted in FIG. 7 ends at block 716.

Referring now to FIG. 8, there is depicted a high level logicalflowchart of an exemplary method by which a lower level cache processesa deallocation request in accordance with one embodiment. Theillustrated process begins at block 800 and then proceeds to block 802,which illustrates a lower level cache, such as an L2 cache 230,receiving a deallocation request from the affiliated processor core 202,preferably via load pipeline 325. As noted above with reference to FIG.3, the deallocation request is loaded into dispatch pipeline 306, whichaccesses directory 308 utilizing the target address specified in thedeallocation request.

If the target address does not hit (i.e., misses) in directory 308, nofurther processing of the deallocation request is performed in the lowerlevel cache. Accordingly, in one embodiment, the deallocation request issimply discarded from dispatch pipeline 306, and the process ends atblock 820. In an alternative embodiment, dispatch pipeline 306 forwardsthe deallocation request to the next lower level cache (e.g., L3 cache232) in the cache hierarchy, as depicted at optional block 816. Inembodiments including block 816, the deallocation request can beprocessed at the next lower level cache in the same manner as depictedin FIG. 8. In at least some embodiments, finer grained cache managementis implemented by including in the deallocation request a hierarchylevel indicator that indicates how far down the cache hierarchy thedeallocation request is to be transmitted. Thus, for example, adeallocation request may specify that the deallocation request is to beprocessed at the L2 and L3 caches, but not at the still lower level L4cache. Following block 816, the process shown in FIG. 8 ends at block820.

Returning to block 810, in response to the target address of thedeallocation request hitting in directory 308, dispatch pipeline 306updates the replacement order recorded for the target cache line todemote the target cache line, thus making the target cache line morelikely to be selected as the victim cache line to be evicted from itscongruence class upon a subsequent miss of a memory access requestmapping to that congruence class (block 812). For example, if L2 cache230 is implementing an LRU or pseudo-LRU replacement policy, dispatchpipeline 306 may update chronology field 418 of the replacement orderfield 416 of the directory entry 410 associated with the target cacheline to LRU (or another predetermined chronology position more likely tobe evicted, such as LRU+1). If L2 cache 230 is implementing a differentreplacement policy, dispatch pipeline 306 updates replacement orderfield 416 accordingly to increase the probability that the target cacheline will be selected as the victim cache line to be evicted from itscongruence class. While updating the replacement order for the targetcache line, dispatch pipeline 306 preferably refrains from modifying thetag field 412 or state field 414 of the directory entry 410 associatedwith target cache line, from accessing the target cache line in dataarray 302, and from dispatching an RC machine 231 to handle thedeallocation request. By servicing the deallocation request entirely indispatch pipeline 306 with reference to directory 308, a sequence ofdeallocation requests, such as deallocation sequence 534 of FIG. 5, canbe serviced at the maximum dispatch rate of dispatch pipeline 306.

As depicted at optional block 814, in performing the update to thedirectory entry 410 associated with the target cache line of thedeallocation request, dispatch pipeline 306 also sets T (transient)field 420 in the directory entry 410 associated with the target cacheline. By setting T field 420, the fact that the associated cache linewas the target of an explicit deallocation request of the processor core202 can be retained as the target cache line traverses the cachehierarchy. Thus, when the target cache line is eventually evicted andsent to a lower level (e.g., L3) cache, the lower level cache canimmediately place the target cache line at a selected position in thereplacement order that makes eviction of the target cache line morelikely (e.g., LRU or LRU+1 rather than MRU).

In addition to block 812 and, if implemented, optional block 814, theprocess performed in the case of a cache hit can optionally also includesending the deallocation request to one or more lower levels of cache,as depicted at block 816 and as described above. The process given inFIG. 8 thereafter ends at block 820.

With reference now to FIG. 9, there is illustrated a high level logicalflowchart of an exemplary method by which a lower level cache services amemory access request of an affiliated processor core 202 in accordancewith one embodiment. The process depicted in FIG. 9 begins at block 900and proceeds to block 902, which illustrates a lower level cache, suchas an L2 cache 230, receiving a memory access request (e.g., a loadrequest or store request) from an affiliated processor core 202. Asdescribed above, the request is processed in dispatch pipeline 306,which performs a lookup in directory 308 to access directory informationof the target cache line, dispatches an RC machine 231 to service thememory access request, and passes the memory access request and thedirectory information for the target cache line to the dispatched RCmachine 231 for handling.

At block 904, the RC machine 231 determines by reference to thedirectory information of the target cache line if the target address ofthe memory access request hit in directory 308 in a coherence state thatpermits the memory access request to be serviced without issuance of anoperation on the interconnect fabric. As will be appreciated, the lowerlevel cache can generally satisfy a non-storage-modifying requestwithout issuing an interconnect operation if state field 414 indicatesany data-valid coherency state for the target cache line. The lowerlevel cache generally cannot satisfy a storage-modifying request withoutissuing an interconnect operation unless state field 414 indicates aModified or Exclusive (or similar) coherency state for the target cacheline.

In response to an affirmative determination at block 904, the processproceeds in some embodiments to block 910, which depicts the RC machine231 performing the actions necessary to service the memory accessrequest without issuance of an operation on the interconnect fabric(e.g., issuing a directory write request and/or providing load data toprocessor core 202 or writing store data to data array 302). Inembodiments implementing T field 420, the RC machine 231 makes anadditional determination at block 906 whether or not the directoryinformation received from dispatch pipeline 306 indicates that the Tfield 420 of the target cache line is set to identify the target cacheline as a target of a previous deallocation request of the affiliatedprocessor core 202. If not, the process passes to block 910, which hasbeen described. If, however, RC machine 231 determines at block 906 thatthe T field 420 is set, the RC machine 231 includes in a directory writerequest a request to set the replacement order field 416 of the targetcache line of the memory access request in accordance with a desiredpolicy (block 908). For example, in various embodiments, RC machine 231may set the target memory block to a predetermined replacement orderposition (e.g., LRU), may increment the replacement order position byone (e.g., update the target memory block from LRU to LRU+1), or mayreset T field 420 and set the replacement order position to MostRecently Used (MRU). The policy for handling a hit on a cache line witha set T field 420 is preferably selected from among these embodiments tomatch the anticipated data access patterns of the current workload. Theprocess passes from block 908 to block 910, which has been described.Following block 910, the process illustrated in FIG. 9 terminates atblock 924.

Returning to block 904, in response to RC machine 231 determining thatthe memory access request cannot be serviced without issuing aninterconnect operation, the process proceeds to block 916. Block 916illustrates RC machine 231 issuing an appropriate interconnect operationon the interconnect fabric to enable the memory access request to beserviced. In general, the interconnect operation includes at least atransaction type and a target address. Following block 916, the processcontinues to block 918, which depicts RC machine 231 receiving acombined response from coherence management logic 210 (FIG. 2). Aspreviously discussed, the combined response is generated by responselogic 210 from partial responses of snoopers within data processingsystem 100 and represents a system wide response to the memory accessrequest.

The process continues to block 920, which shows RC machine 231determining if the combined response of the interconnect operationindicates “success” or “retry”. If the combined response indicates“retry” (that the request cannot be fulfilled at the current time andmust be retried), the process returns to block 916, which has beendescribed. If the combined response indicates “success” (that therequest can be fulfilled at the current time), the process continues toblock 922, which illustrates RC machine 231 performing operations toservice the memory access request, as indicated by the combinedresponse. For example, if the request of the interconnect operation wasa read operation, RC machine 231 causes the requested data received fromthe interconnect fabric to be supplied to the processor core 202, theread data to be installed in data array 302, and update to be performedto directory 308. If on the other hand, the interconnect operation was astore-type operation, RC machine 231 causes cache array 302 to beupdated with the store data provided by the requesting processing unit202 and directory 308 to be updated.

In either case, if the target cache line did not reside in data array302 prior to the interconnect operation, RC machine 231 causes a COmachine 310 to be dispatched to evict a victim cache line and associateddirectory information from the congruence class to which the targetaddress of the memory access request maps. If the lower level cache isan L2 cache 230, CO machine 310 preferably casts out the victim cacheline to one of L3 caches 232 via a castout operation. In embodiments inwhich T fields 420 are implemented within directory entries 410, thedirectory information transmitted to the L3 cache 232 in castoutoperation includes the setting of the T field 420 (i.e., an indicationof whether the cache line was the target of a previous deallocationrequest of the affiliated processor core 202). Following block 922, theexemplary process depicted in FIG. 9 terminates at block 924.

Referring now to FIG. 10, there is depicted a high level logicalflowchart of an exemplary process by which a lower level cache,hereinafter assumed to be an L3 cache 232, handles a castout of a higherlevel cache, hereinafter assumed to be an L2 cache 230, in accordancewith one embodiment. The process begins at block 1000 of FIG. 10 andthen proceeds to block 1002, at which the process iterates until the L3cache 232 receives a cast-in request 264 from the associated L2 cache230. In response to receipt of a cast-in request 264, L3 cache 232writes the directory information and data, if any, received in thecast-in request 264 in the directory and data array, respectively, of L3cache 232 (block 1004). Depending on the coherence protocol implementedin the data processing system 100, the castout cache line may beassociated with a different coherence state in L3 cache 232 than thecastout cache line had when evicted from L2 cache 230.

In embodiments in which T field 420 is not implemented, L3 cache 232sets the replacement order field 416 in the L3 cache directory for thecache line to MRU, as shown at block 1008. In alternative embodimentsthat implement T field 420, L3 cache 232 also checks to see if the Tfield 420 associated with the castout cache line is set in the directoryinformation supplied in the cast-in request 264 (block 1006). If not,the process proceeds to block 1008, as has been described. If, however,L3 cache 232 determines at block 1006 that the T field 420 associatedwith the castout cache line is set, L3 cache 232 sets the replacementorder field 416 for the cache line to a designated replacement orderposition that makes it more likely for the cache line to be evicted fromL3 cache 232 (e.g., LRU or LRU+1) in response to a subsequent cast-inrequest 264, as shown at block 1010. Following either block 1008 orblock 1010, the process shown in FIG. 10 ends at block 1012.

In at least one embodiment, a data processing system includes aprocessor core supported by upper and lower level caches. In response toexecuting a deallocate instruction in the processor core, a deallocationrequest is sent from the processor core to the lower level cache, thedeallocation request specifying a target address associated with atarget cache line. In response to receipt of the deallocation request atthe lower level cache, a determination is made if the target addresshits in the lower level cache. In response to determining that thetarget address hits in the lower level cache, the target cache line isretained in a data array of the lower level cache and a replacementorder field in a directory of the lower level cache is updated such thatthe target cache line is more likely to be evicted from the lower levelcache in response to a subsequent cache miss.

In at least one embodiment, in response to a subsequent cache miss tothe congruence class including target cache line, the lower level cachecasts out the target cache line to a still lower level cache with anindication that the target cache line was a target of a previousdeallocation request of the processor core. In response to theindication, the replacement order field in a directory of the stilllower level cache is updated such that the target cache line is morelikely to be evicted from the still lower level cache.

While one or more embodiments have been particularly shown anddescribed, it will be understood by those skilled in the art thatvarious changes in form and detail may be made therein without departingfrom the spirit and scope of the invention. For example, althoughaspects of the present invention have been described with respect todata processing system hardware, it should be understood that one ormore embodiments of the present invention may alternatively beimplemented as a program product for use with a data processing system.Such program product(s) include(s) a tangible computer readable storagedevice/medium that stores program code that directs the functions of thepresent invention. The computer readable storage device/medium may beimplemented, for example, as a CD-ROM, DVD, diskette or hard disk,system memory, flash memory, etc.

As an example, the program product may include data and/or instructionsthat when executed or otherwise processed on a data processing systemgenerate a logically, structurally, or otherwise functionally equivalentrepresentation (including a simulation model) of hardware components,circuits, devices, or systems disclosed herein. Such data and/orinstructions may include hardware-description language (HDL) designentities or other data structures conforming to and/or compatible withlower-level HDL design languages such as Verilog and VHDL, and/or higherlevel design languages such as C or C++. Furthermore, the data and/orinstructions may also employ a data format used for the exchange oflayout data of integrated circuits and/or symbolic data format (e.g.information stored in a GDS11 (GDS2), GL1, OASIS, map files, or anyother suitable format for storing such design data structures).

1.-11. (canceled)
 12. A processing unit, comprising: a processor coreincluding an upper level cache, wherein the upper level cache, inresponse to executing a deallocate instruction, sends a deallocationrequest specifying a target address associated with a target cache line;and a lower level cache coupled to the processor core, the lower levelcache including a data array, a directory of contents of the data array,and control logic, wherein the control logic, in response to receipt ofthe deallocation request at the lower level cache, determines if thetarget address hits in the directory and, in response to determiningthat the target address hits in the directory, retains the target cacheline in the data array and updates a replacement order field in thedirectory such that the target cache line is more likely to be evictedfrom the lower level cache in response to a subsequent cache miss in acongruence class including the target cache line.
 13. The processingunit of claim 12, wherein, in response to receipt of the deallocationrequest, the control logic updates the replacement order field to makethe target cache line least recently used (LRU).
 14. The processing unitof claim 12, wherein the control logic thereafter deallocates the targetcache line from the lower level cache in response to a data accessrequest missing in the lower level cache.
 15. The processing unit ofclaim 12, wherein the control logic thereafter, in response to an accessof the target cache line in the lower level cache prior to eviction ofthe target cache line from the lower level cache, refrains from updatingthe replacement order field.
 16. The processing unit of claim 12,wherein: the lower level cache includes a load and store pipelines fordata access requests of the processor core; and the lower level cacheprocesses the deallocation request in the load pipeline.
 17. Theprocessing unit of claim 12, wherein the processor core executes thedeallocate instruction at completion of processing of a datasetincluding the target cache line and a plurality of other cache lines topromote eviction of the dataset from the lower level cache.
 18. Theprocessing unit of claim 12, wherein: the lower level cache is inclusiveof contents of the upper level cache; and the processor core sends thedeallocation request to the lower level cache regardless of whether ornot the target address hits in the upper level cache.
 19. The processingunit of claim 12, wherein: control logic includes a plurality of statemachines that service processor data access requests; and the controllogic services the deallocation request without allocating one of theplurality of state machines to the deallocation request.
 20. Theprocessing unit of claim 12, wherein the control logic, in response todetermining that the target address hits in the lower level cache,retains a previous coherence state associated with the target cache linein the cache directory.
 21. A data processing system, comprising: aplurality of processing units including the processing unit of claim 10;an interconnect fabric coupling the plurality of processing units; and asystem memory coupled in communication with the interconnect fabric.